Hi, we're aware of this issue and annoyed ourselves we can't handle it sooner.
In a future version in a next few weeks there will be an option to increase the timeout value which shall reduce chances of this error appearing.
In a few months hopefully there will auto retry with exponential backoff, so even if it fails it will retry for you couple times, until it needs manual intervention.
Thanks! (edited)